chore(monitor): remove Sentry reporting from tests#3300
Merged
Conversation
They haven't been terribly enlightening so far, and so I'd like to stop wasting our Sentry quota/rate limit on it.
joshlarson
approved these changes
Jul 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
Sentry: MBTA-DOTCOM-WT
Implementation
We periodically run a series of Playwright tests against the live application to monitor whether things are still working as expected. These tests sometimes fail -- a while ago, we added this feature which reports the failure in Sentry and saves it with a screenshot. However, the feature hasn't been terribly helpful. Example below:
We get the test failures reported in Splunk, regardless. So to avoid these sorts of errors from filling up our Sentry quota, I'm removing this feature.